After you add a Web Services trading pickup to a community, you can view and modify pickup characteristics.
Add a Web Services trading pickup
Enable this pickup
Select or de-select this option to enable or disable the pickup.
Name
Name of the pickup.
Make this the default delivery
Select this option if you have multiple exchanges and you want this pickup to be selected for the community default pickup.
Local URL
The local port and path the embedded HTTP server uses.
URL used by partners
The fully qualified host name or IP address, port number and path where partners must connect to send messages.
When you export your community profile as a partner profile, the URL becomes part of your exported partner profile. The host, port and path may be different than the values in the local URL. If your network uses a load balancer or firewall, contact your network administrator for the correct value.
If your local URL is HTTP and you use an SSL terminator in the DMZ for inbound connections, the partner must send messages to the terminator and not to Activator. You must specify the HTTPS URL of the terminator as the URL used by partners. Make sure the terminator can forward messages to Activator. Your partner also must import and trust the public-key certificate from your SSL terminator. Activator cannot include this certificate when the community profile is exported as a partner profile.
When partners are required to connect to the server with user names and passwords, you can view and create user accounts on the Accounts tab.
Web Services user
To create a user account click Add and then complete the fields: User name, Password, and Transport user password policy – From the drop-down list, select a password policy to apply to this account.
Partner
Users accounts owned by specific partners can also be added to the exchange. To enable server access for the account of a specific partner, click Add, then select a partner from the list of available partners, and select an account from the list of accounts that belong to that partner.
By default, exchange points are active continuously. You can add active schedules by day of the week and time of day. For example, if you select Monday 0:00 - 23:59, the exchange is on all day every Monday. If you select Monday 8:30 - 11:30, the exchange is on from 8:30 to 11:30 a.m. and off all other times on Mondays.
WSDL 1.1 file
Use this field and the following field to implement a custom Web Service for use by Activator. To support ?wsdl and/or ?wsdl2 queries, the custom Web Service must create the appropriate wsdl or wsdl2 file or both. Use one or both of these fields to point to the custom file or files.
WSDL 2.0 file
See WSDL file field description above.
Generate new WSDL
Use this command to open the WSDL configuration wizard and define a new service.
Parse SOAP headers into message metadata
Select this option if you want to SOAP headers to be carried as metadata attributes with the message.
XPath reference to SOAP header to parse
If you selected the previous option (Parse SOAP headers into message metadata), enter an XPath expression to resolve the header.
Click Add to display the Local XPath field and then enter an XPath expression. Enter any legal XPath expression. Xpath wildcard syntax is permitted. If the expression resolves to more than one node, only the value of the first matching node is included in the metadata value.
To define multiple headers, click Add multiple times and enter an expression in each field.
Process SOAP body
Select this option to process the contents of the SOAP body.
Process attachments
Select this option to process the attachments of the SOAP message.
Receive handler config file
The file to use when unpacking a message. The default file is axis2.xml. The file is in located in <install directory>\conf.
Synchronous response generated in back end
Select this option to have the back-end application generate synchronous responses.
If this option is not selected, the synchronous response is generated within Activator. By default, this option is not selected.
If this option is selected, Activator keeps open the inbound HTTP connection so a synchronous response payload can be built by the back-end system. Once Activator receives it, the response is packaged and sent over the open HTTP connection. If selected, you must create an MMD for Activator to pick up from integration. Make sure to remove any custom service from the repository that builds responses within Activator. This is the mostly likely option if you do not have the optional Software Development Kit. By default, this option is not selected.
You also must create an Axis service that builds the response. The service must use the message receiver, defined within Activator, that receives the original message and helps in handling and sending the response built by your service. If Activator cannot find a service, the connection is closed with an HTTP 204 response.
Timeout to apply for out of sequence messages (seconds)
Default = 60 seconds. Enter a time limit for Activator to wait for missing messages of a sequence before taking the appropriate action. This feature avoids the blocking of processing when a sequenced message is not available.
Back up the files that go through this transport
Select this option to have the system back up copies of the messages it receives from partners. Backing up files is strongly recommended. This is required for the system to perform fail-over operations such as attempting to send messages again (retries) in case of a transport connection failure. Without backups, a message in process cannot be recovered if the server stops or restarts. Backups also are needed if you want the ability to resend messages to partners. Backup files are stored in <install directory>\common\data\backup, unless you specify otherwise.
Process consumed messages using community delivery settings
Select this option if you want Activator to perform routing based only on the delivery criteria that are specified in the community. When you select this option, no other Activator-related processing is performed on consumed messages.
Restrict maximum file size for this transport
Select this option to specify the maximum size of files the transport can handle. If Activator receives a file larger than the maximum, the file is rejected and a message is written to the events log. If received via HTTP, a 413 response also is sent and the connection is closed. A 413 message is Request Entity Too Large. The maximum size must be expressed in bytes. Do not use commas. For instance, a kilobyte is 1024 bytes, a megabyte is 1048576 bytes, a gigabyte is 1073741824 bytes. The smallest maximum allowed is 1000 bytes. On the opposite extreme, you can enter the largest number the field can accommodate.